Unactionable incident?

#1

Hello.

Iā€™m becoming more acquainted with the Intelligent Dashboard feature. The Incident List for my team contains a column called ā€œUnactionableā€. Iā€™m unclear at this point as to what criteria PagerDuty is using to determine this on a per-incident level.

Internally, we use the Jira integration, and use the presence of an accompanying Jira issue to determine whether an incident was actionable or not, which can be a bit of a manual endeavor to analyze. However, if thereā€™s a better, more automated way of determining this, Iā€™m game. I just need to know how itā€™s determined. Anyone know?

Thanks!

#2

Hi Ryan: An unactionable incident is defined one that is resolved within two minutes. Typically this is because it was triggered off some condition that was transient & resolved itself without human intervention.

Hope that helps.

1 Like
#3

Suggestionā€¦why not call this nonactionable, or self-resolving? Unactionable sounds like you ā€œcanā€™tā€ perform any action, as opposed to ā€œno need to take actionā€. The verbiage is a bit misleading.

#4

Hi Ryan and Bryan:
As Julian mentioned, we currently mark incidents that are resolved within 120 seconds as unactionable. These could be auto resolved or resolved by a responder. I like the ā€˜no need to take actionā€™ approach. Will make sure to look at alternatives when we tackle updates to the intelligent dashboards.

Thank you.

#5

Thanks for the explanation. Actually, I went to look at the data again, and it looks like the Unactionable column is no longer in the Intelligent Dashboard Incident List. Was it removed?

#6

Hi Ryan,
Yes, the Unactionable column was removed because the use-case that required it was also removed.
Thank you.